Skip to content

Conversation

@dinhlongviolin1
Copy link
Contributor

@dinhlongviolin1 dinhlongviolin1 commented Sep 11, 2025

Describe Your Changes

  • Optimized desktop build (no extension web)

Fixes Issues

Self Checklist

  • Added relevant comments, esp in complex areas
  • Updated docs (for bug fixes / features)
  • Created issues for follow-up changes or refactoring needed

Important

Exclude @jan/extensions-web from desktop build in vite.config.ts.

  • Build Optimization:
    • Exclude @jan/extensions-web from dependency optimization in vite.config.ts.
    • Mark @jan/extensions-web as external in the Rollup options in vite.config.ts.

This description was created by Ellipsis for 758b988. You can customize this summary. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to 758b988 in 1 minute and 31 seconds. Click for details.
  • Reviewed 19 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. web-app/vite.config.ts:34
  • Draft comment:
    Add inline comment to explain why '@jan/extensions-web' is excluded in optimizeDeps.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is a build configuration change that excludes a specific package from optimization. While documentation can be helpful, the suggestion is asking for explanation rather than pointing out a clear issue. The comment is more of a "nice to have" than identifying a problem that needs fixing. Per the rules, we should not make purely informative comments or ask for explanations. Perhaps understanding why this package is excluded is important for maintainability and could prevent future issues if someone removes this configuration without knowing its purpose. While documentation can be valuable, our rules explicitly state not to make purely informative comments or ask for explanations. The code change itself is clear and functional without the suggested comment. Delete this comment as it only requests additional documentation without identifying any actual code issues that need fixing.
2. web-app/vite.config.ts:38
  • Draft comment:
    Include a brief comment on why '@jan/extensions-web' is marked external in rollupOptions.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to provide additional information about a specific configuration in the code. It is not a direct code suggestion or a request for a test, and it doesn't point out a potential issue or improvement. It seems to be asking for clarification, which violates the rule against asking the PR author to explain or confirm their intention.

Workflow ID: wflow_SrF0BkrILxVq4eFR

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@github-actions
Copy link
Contributor

Barecheck - Code coverage report

Total: 29.43%

Your code coverage diff: 0.00% ▴

Uncovered files and lines
FileLines
web-app/vite.config.ts1-8, 11, 13, 15-59, 61, 63-71, 76, 78-89, 91-95

@github-actions
Copy link
Contributor

@dinhlongviolin1 dinhlongviolin1 merged commit ea72c1a into dev Sep 11, 2025
22 checks passed
@github-project-automation github-project-automation bot moved this to QA in Jan Sep 11, 2025
@dinhlongviolin1 dinhlongviolin1 deleted the feat/optimzed-build branch September 11, 2025 12:51
@github-actions github-actions bot added this to the v0.6.10 milestone Sep 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants